-
Notifications
You must be signed in to change notification settings - Fork 38
SHACL Rules - content planning #554
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: gh-pages
Are you sure you want to change the base?
Conversation
<p> | ||
See SHACL AF <a href="https://www.w3.org/TR/shacl-af/#rules-syntax">`sh:rule`</a>, | ||
which describes <a href="https://w3c.github.io/shacl/shacl-af/index.html#TripleRule">triple rules</a>, | ||
with a special case of <a href="https://w3c.github.io/shacl/shacl-af/index.html#PropertyValueRule"> property value rules</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with a special case of <a href="https://w3c.github.io/shacl/shacl-af/index.html#PropertyValueRule"> property value rules</a> | |
with special cases | |
of <a href="https://w3c.github.io/shacl/shacl-af/index.html#PropertyValueRule"> property value rules</a> |
At one level, nothing needs top done because they have separate evaluation | ||
and it is only a matter of whether an engine supports them or not. | ||
It might be helpful to say when they happen (before 1.2 Rules - seea also defaul values) | ||
and can infer if they generate infered triple. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At one level, nothing needs top done because they have separate evaluation | |
and it is only a matter of whether an engine supports them or not. | |
It might be helpful to say when they happen (before 1.2 Rules - seea also defaul values) | |
and can infer if they generate infered triple. | |
At one level, nothing needs to be done because they have separate evaluation | |
and it is only a matter of whether an engine supports them or not. | |
It might be helpful to say when they happen (before 1.2 Rules — see also default values) | |
and can infer whether they generate inferred triple. |
<p>@@ Discussion</p> | ||
<p> Define a new rule that is another rule with some variables already set</p> | ||
<ul> | ||
<li>Where do the setting come from?</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<li>Where do the setting come from?</li> | |
<li>Where do the settings come from?</li> |
<h2>More on evaluation</h2> | ||
<div class="ednote"> | ||
<p>@@ Discussion</p> | ||
<p>The main evaluatiuon description creates all inferred triple using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<p>The main evaluatiuon description creates all inferred triple using | |
<p>The main evaluation description creates all inferred triples using |
<p>Negation (e.g. via SPARQL `NOT EXISTS`/`EXISTS`) can allowed if | ||
the pattern is executed only one the base data graph, not including the | ||
inferred graph. i.e. inferred triples are not seen. | ||
Or stratification - not seeing inferred tripels from the current stratum. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<p>Negation (e.g. via SPARQL `NOT EXISTS`/`EXISTS`) can allowed if | |
the pattern is executed only one the base data graph, not including the | |
inferred graph. i.e. inferred triples are not seen. | |
Or stratification - not seeing inferred tripels from the current stratum. | |
<p>Negation (e.g., via SPARQL `NOT EXISTS`/`EXISTS`) can be allowed if | |
the pattern is executed only on the base data graph, not including the | |
inferred graph, i.e., inferred triples are not seen. | |
Or stratification — not seeing inferred triples from the current stratum. |
Assignment takes the rule lanuage outside datalog. | ||
Can we define when it is "safe"? (e.g. triples involving the assignment | ||
are not mentioned in the body of any other rule). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assignment takes the rule lanuage outside datalog. | |
Can we define when it is "safe"? (e.g. triples involving the assignment | |
are not mentioned in the body of any other rule). | |
Assignment takes the rule language outside datalog. | |
Can we define when it is "safe" (e.g., triples involving the assignment | |
are not mentioned in the body of any other rule)? |
Currently, SHACL Rules is, in datatlog-speak, only unnamed 3-tuples. | ||
To support "programming" in rules, should we allow transient (not part of the output, | ||
only during rulset evaluation) named n-tuples? <br/> | ||
e.g. <code>name(termOrVar, ...)</code>, possibly with a unique marker e.g. <code>`</code> | ||
giving <code>`name(termOrVar, ...)</code>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, SHACL Rules is, in datatlog-speak, only unnamed 3-tuples. | |
To support "programming" in rules, should we allow transient (not part of the output, | |
only during rulset evaluation) named n-tuples? <br/> | |
e.g. <code>name(termOrVar, ...)</code>, possibly with a unique marker e.g. <code>`</code> | |
giving <code>`name(termOrVar, ...)</code>. | |
Currently, SHACL Rules are, in datatlog-speak, only unnamed 3-tuples. | |
To support "programming" in rules, should we allow transient (not part of the output, | |
only during rulset evaluation) named n-tuples? <br/> | |
e.g., <code>name(termOrVar, ...)</code>, possibly with a unique marker, e.g., | |
<span class="codepoint" translate="no"><bdi lang="en">`</bdi> | |
<code class="uname">U+0060 grave accent</code></span> | |
giving <code>`name(termOrVar, ...)</code>. |
<pre class="example-rules"> | ||
PREFIX : <http://example/> | ||
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> | ||
PREFIX shr <http://www.w3.org/ns/shacl-rules#> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so is this now shr or slr?
This is a sketch for discussion and refinement; do not merge.
Editors noted added at section 6.